Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac0ddf0f2d1f0454a5bb0fcdb3edabd9aa4b2ed7dee26acb96c34858543f973

Tx prefix hash: 9ea5b6f6eb614ea8b641b22007bd956134b529009bd25d053eede62f12b2d81b
Tx public key: 20b24c9487934e836b1b3148f885125bdc7f4fefdf4c9dd5c5d27f6e4658572c
Timestamp: 1703211770 Timestamp [UCT]: 2023-12-22 02:22:50 Age [y:d:h:m:s]: 01:103:18:11:52
Block: 918367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335277 RingCT/type: yes/0
Extra: 0120b24c9487934e836b1b3148f885125bdc7f4fefdf4c9dd5c5d27f6e4658572c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08528adefb914f8512585f1e3f07abded9ca57482d8d63793528cf2b87c7ea09 0.600000000000 1376011 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": 918377, "vin": [ { "gen": { "height": 918367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08528adefb914f8512585f1e3f07abded9ca57482d8d63793528cf2b87c7ea09" } } ], "extra": [ 1, 32, 178, 76, 148, 135, 147, 78, 131, 107, 27, 49, 72, 248, 133, 18, 91, 220, 127, 79, 239, 223, 76, 157, 213, 197, 210, 127, 110, 70, 88, 87, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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