Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557b9d35d47b8ca023cbbe9a880ac9e7b2a6d0af06f473a19d7caa883a42c47d

Tx prefix hash: e3b21ad561eff8c4704c9772f7c120b0d7dd41e473c23aa1d66978ad44006801
Tx public key: de03c5855dee7bbe52ef7a93e16b6358c84d6c5d8257150df18e17392053e33f
Timestamp: 1752690040 Timestamp [UCT]: 2025-07-16 18:20:40 Age [y:d:h:m:s]: 00:132:21:02:49
Block: 1326875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93748 RingCT/type: yes/0
Extra: 01de03c5855dee7bbe52ef7a93e16b6358c84d6c5d8257150df18e17392053e33f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46632e560111717dfea9aae07c29c6f5cc2dd79c119ed2377b2156d40ee94836 0.600000000000 1814628 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": 1326885, "vin": [ { "gen": { "height": 1326875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46632e560111717dfea9aae07c29c6f5cc2dd79c119ed2377b2156d40ee94836" } } ], "extra": [ 1, 222, 3, 197, 133, 93, 238, 123, 190, 82, 239, 122, 147, 225, 107, 99, 88, 200, 77, 108, 93, 130, 87, 21, 13, 241, 142, 23, 57, 32, 83, 227, 63, 2, 17, 0, 0, 0, 1, 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