Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9eeea9cba436691b98eaaa3d900cd1b1a1a179745cca28146f16466b702c91

Tx prefix hash: 5066e1fc3686184835e72619f195a3379bf46bf74bd59bf5cddf6dc51d0d028d
Tx public key: 3e516b0c9de08f8553acc5443bdf3420faf165a3fd0f1fd015a18ba8eeeb9a30
Timestamp: 1713943359 Timestamp [UCT]: 2024-04-24 07:22:39 Age [y:d:h:m:s]: 00:357:15:10:12
Block: 1007344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255658 RingCT/type: yes/0
Extra: 013e516b0c9de08f8553acc5443bdf3420faf165a3fd0f1fd015a18ba8eeeb9a3002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842fd879413ef6db91242ef5ec1f78950de5e35be57a7137c220617fb2a6aea3 0.600000000000 1468654 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": 1007354, "vin": [ { "gen": { "height": 1007344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842fd879413ef6db91242ef5ec1f78950de5e35be57a7137c220617fb2a6aea3" } } ], "extra": [ 1, 62, 81, 107, 12, 157, 224, 143, 133, 83, 172, 197, 68, 59, 223, 52, 32, 250, 241, 101, 163, 253, 15, 31, 208, 21, 161, 139, 168, 238, 235, 154, 48, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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