Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fdc684e44644fcbbd841e6e559e7c3e16685dc9ce2e9669e8ffcc60120b28b2

Tx prefix hash: 08c3f791d6e7fe83098878195de3173c927460b872e86f13f685c843c607a997
Tx public key: 4876917f46fad638cb30bbb5c4b9f68ffe086e6a664707df8258ff569b1499b5
Timestamp: 1725721180 Timestamp [UCT]: 2024-09-07 14:59:40 Age [y:d:h:m:s]: 00:123:14:16:49
Block: 1104991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88389 RingCT/type: yes/0
Extra: 014876917f46fad638cb30bbb5c4b9f68ffe086e6a664707df8258ff569b1499b502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae9e5eaa8e82e76ec06af56b91a2e5c97537ed8098f0eaa68cfaf0117a3cb6c2 0.600000000000 1582326 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": 1105001, "vin": [ { "gen": { "height": 1104991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae9e5eaa8e82e76ec06af56b91a2e5c97537ed8098f0eaa68cfaf0117a3cb6c2" } } ], "extra": [ 1, 72, 118, 145, 127, 70, 250, 214, 56, 203, 48, 187, 181, 196, 185, 246, 143, 254, 8, 110, 106, 102, 71, 7, 223, 130, 88, 255, 86, 155, 20, 153, 181, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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