Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d2defb7b796846c6ea2c4d5a2899b008e7ee03a5a88fa32afd5530b9c88fe1

Tx prefix hash: 9786502e5b48d39567ff45685296d94f36b2e0b8f9b50bafd9a7bf188c94a80f
Tx public key: e972892e7ce9f3188d90f86905afd8e9f6e1f8c39c2c0d383ecec0e2a5e05975
Timestamp: 1733876311 Timestamp [UCT]: 2024-12-11 00:18:31 Age [y:d:h:m:s]: 01:010:21:21:48
Block: 1172490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266217 RingCT/type: yes/0
Extra: 01e972892e7ce9f3188d90f86905afd8e9f6e1f8c39c2c0d383ecec0e2a5e059750211000000016e963a0b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2916af14cdb3d7e33859c1afb15cd197783d0a1413187056a3a695e56827fa 0.600000000000 1658391 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": 1172500, "vin": [ { "gen": { "height": 1172490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2916af14cdb3d7e33859c1afb15cd197783d0a1413187056a3a695e56827fa" } } ], "extra": [ 1, 233, 114, 137, 46, 124, 233, 243, 24, 141, 144, 248, 105, 5, 175, 216, 233, 246, 225, 248, 195, 156, 44, 13, 56, 62, 206, 192, 226, 165, 224, 89, 117, 2, 17, 0, 0, 0, 1, 110, 150, 58, 11, 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