Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ca30ec3c4d53cc09fa942e9f06e32653070aa88f94c4dd7c755d5969915d0fc

Tx prefix hash: 975f2b8f2da32ec4bd13e29d25d02146ac4d706f9fb879f4efaa4df62c46c034
Tx public key: e0d8d3e74ddd7dc8e86c6eb7c45f4cbcb87e09196b99a138b54ed99c26641c46
Timestamp: 1744096564 Timestamp [UCT]: 2025-04-08 07:16:04 Age [y:d:h:m:s]: 00:289:18:18:56
Block: 1256819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204784 RingCT/type: yes/0
Extra: 01e0d8d3e74ddd7dc8e86c6eb7c45f4cbcb87e09196b99a138b54ed99c26641c460211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f01473b61eae75d6a75ae108e5afb6271067b82bf10ea44338329beaee028236 0.600000000000 1743936 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": 1256829, "vin": [ { "gen": { "height": 1256819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f01473b61eae75d6a75ae108e5afb6271067b82bf10ea44338329beaee028236" } } ], "extra": [ 1, 224, 216, 211, 231, 77, 221, 125, 200, 232, 108, 110, 183, 196, 95, 76, 188, 184, 126, 9, 25, 107, 153, 161, 56, 181, 78, 217, 156, 38, 100, 28, 70, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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