Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e8576b06399b7413b374abced1af3b58ac359c26e811f7503c6a7f79035a20

Tx prefix hash: 103e9e2fd05dd98d33bb7030f43ce004d9010af55886321c7f85f34c017cbb21
Tx public key: 245aa2e35ed10c984b1f2fdbd4010ab5673148019ab27c9d7e5b060ce6d24e26
Timestamp: 1716188404 Timestamp [UCT]: 2024-05-20 07:00:04 Age [y:d:h:m:s]: 01:171:05:19:43
Block: 1025959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380967 RingCT/type: yes/0
Extra: 01245aa2e35ed10c984b1f2fdbd4010ab5673148019ab27c9d7e5b060ce6d24e2602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc40836ef0ceaf242d3fd9c9e37b62b4d12afc10e62c8cb77bca2f9abf0c3819 0.600000000000 1492780 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": 1025969, "vin": [ { "gen": { "height": 1025959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc40836ef0ceaf242d3fd9c9e37b62b4d12afc10e62c8cb77bca2f9abf0c3819" } } ], "extra": [ 1, 36, 90, 162, 227, 94, 209, 12, 152, 75, 31, 47, 219, 212, 1, 10, 181, 103, 49, 72, 1, 154, 178, 124, 157, 126, 91, 6, 12, 230, 210, 78, 38, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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