Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503e7e36036e6235598c408a5ac86d7464ef3d5c5e02b29fcc2bfd2238f86a2c

Tx prefix hash: 9ce0b8d6becd4346c4c941cfe11893f48ca37960f2d6c7d8ba035c5bf07ed6fb
Tx public key: a45b50f81317950c989e6a70c96dd00c901c56b532a248bc3fe5c2117d77425e
Timestamp: 1736764207 Timestamp [UCT]: 2025-01-13 10:30:07 Age [y:d:h:m:s]: 00:065:00:04:29
Block: 1196398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46246 RingCT/type: yes/0
Extra: 01a45b50f81317950c989e6a70c96dd00c901c56b532a248bc3fe5c2117d77425e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9145f52a55dbb4edf94adf9f437a0c7ca74622badeb64c966db91027d5e9ad92 0.600000000000 1682997 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": 1196408, "vin": [ { "gen": { "height": 1196398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9145f52a55dbb4edf94adf9f437a0c7ca74622badeb64c966db91027d5e9ad92" } } ], "extra": [ 1, 164, 91, 80, 248, 19, 23, 149, 12, 152, 158, 106, 112, 201, 109, 208, 12, 144, 28, 86, 181, 50, 162, 72, 188, 63, 229, 194, 17, 125, 119, 66, 94, 2, 17, 0, 0, 0, 6, 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