Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30033b4d7900bb2c41a3402c94d4668414ad36bf63c2962f720c5e075b60c3df

Tx prefix hash: 4f590bc492452f1aa4fefe118d7cc2a9df054fed654567db24ad840b6ff337f8
Tx public key: 3cea73f89171c406844aa197e61ae1fdf7b1860cd6b4dd469d6ee53c1e82c20b
Timestamp: 1749764947 Timestamp [UCT]: 2025-06-12 21:49:07 Age [y:d:h:m:s]: 00:152:09:45:01
Block: 1303720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106640 RingCT/type: yes/0
Extra: 013cea73f89171c406844aa197e61ae1fdf7b1860cd6b4dd469d6ee53c1e82c20b021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdcdb83a0d7e98163fd98dd2bf606ec6ab2ce404f24e514c624c1daca2b224e0 0.600000000000 1791303 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": 1303730, "vin": [ { "gen": { "height": 1303720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdcdb83a0d7e98163fd98dd2bf606ec6ab2ce404f24e514c624c1daca2b224e0" } } ], "extra": [ 1, 60, 234, 115, 248, 145, 113, 196, 6, 132, 74, 161, 151, 230, 26, 225, 253, 247, 177, 134, 12, 214, 180, 221, 70, 157, 110, 229, 60, 30, 130, 194, 11, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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