Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21175adbcac25e51c363c0e3d1a5c5ce78d754071e24af0891c95b9d28d2ab82

Tx prefix hash: 2964ddcfe446b9ee62e06472ff4d18ab346250199ebe16b4e85c6671423a07b4
Tx public key: 4c1df2eabc301203c8f52800d0dbe878fa1c3ef992b7efb76b1fb6ccc79d26cb
Timestamp: 1732994118 Timestamp [UCT]: 2024-11-30 19:15:18 Age [y:d:h:m:s]: 00:121:16:55:49
Block: 1165192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86767 RingCT/type: yes/0
Extra: 014c1df2eabc301203c8f52800d0dbe878fa1c3ef992b7efb76b1fb6ccc79d26cb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08fbdb36627ead842ce676414372c40b640d12a492e068ce0239dd9a8792fd6d 0.600000000000 1650867 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": 1165202, "vin": [ { "gen": { "height": 1165192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08fbdb36627ead842ce676414372c40b640d12a492e068ce0239dd9a8792fd6d" } } ], "extra": [ 1, 76, 29, 242, 234, 188, 48, 18, 3, 200, 245, 40, 0, 208, 219, 232, 120, 250, 28, 62, 249, 146, 183, 239, 183, 107, 31, 182, 204, 199, 157, 38, 203, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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