Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e6d4311752e24ffc9bb760c8cea96eef803010eeff1c691fbdceb4bb829e88

Tx prefix hash: 64443eb587eb7e285c5c5f1cae534796dc2695700e7a6f3b75c7373f183260f8
Tx public key: 06950de3e2e3f9d83ef4daaead802407470f7b2f6733db727fd02546d7e86d51
Timestamp: 1756624709 Timestamp [UCT]: 2025-08-31 07:18:29 Age [y:d:h:m:s]: 00:120:02:07:42
Block: 1358218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85856 RingCT/type: yes/0
Extra: 0106950de3e2e3f9d83ef4daaead802407470f7b2f6733db727fd02546d7e86d51021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a054e66e5d3713ea8811d6e703e938254376370a28b282e8963443a536a451a 0.600000000000 1846229 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": 1358228, "vin": [ { "gen": { "height": 1358218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a054e66e5d3713ea8811d6e703e938254376370a28b282e8963443a536a451a" } } ], "extra": [ 1, 6, 149, 13, 227, 226, 227, 249, 216, 62, 244, 218, 174, 173, 128, 36, 7, 71, 15, 123, 47, 103, 51, 219, 114, 127, 208, 37, 70, 215, 232, 109, 81, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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