Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bada8099cbf424a9743abb8002fe3c30804ae910b40da85b8c550700cbd430f4

Tx prefix hash: bf0cd34e1a5dfdc75164b947082a891d2a080c34e87d4afb1933665000d3eef3
Tx public key: 6aa802b24aed8ebe65abec053d67c8ef4895985686ca994cfcca7f680e4a2ddb
Timestamp: 1734579992 Timestamp [UCT]: 2024-12-19 03:46:32 Age [y:d:h:m:s]: 00:332:05:07:28
Block: 1178350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234916 RingCT/type: yes/0
Extra: 016aa802b24aed8ebe65abec053d67c8ef4895985686ca994cfcca7f680e4a2ddb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48a9685b11d36f53f55b2acd19dece6add12f4a72dbe13ac1aa810c40138c8a5 0.600000000000 1664737 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1178360, "vin": [ { "gen": { "height": 1178350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48a9685b11d36f53f55b2acd19dece6add12f4a72dbe13ac1aa810c40138c8a5" } } ], "extra": [ 1, 106, 168, 2, 178, 74, 237, 142, 190, 101, 171, 236, 5, 61, 103, 200, 239, 72, 149, 152, 86, 134, 202, 153, 76, 252, 202, 127, 104, 14, 74, 45, 219, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8