Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739cf05dc4d5686f1670603da8358520cdd4bbbcc4a886728c5ed2359bd86971

Tx prefix hash: d6f560441fc71d168dc57992e57dbb09db9054243d6f22f7ae2bdb1d08384f1e
Tx public key: 9c25f5c7fb426cd20fa6d7dd9827dfdae0c083d5326b7af727701b16d2bb7461
Timestamp: 1715896842 Timestamp [UCT]: 2024-05-16 22:00:42 Age [y:d:h:m:s]: 00:325:00:22:25
Block: 1023543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232290 RingCT/type: yes/0
Extra: 019c25f5c7fb426cd20fa6d7dd9827dfdae0c083d5326b7af727701b16d2bb746102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5003ab63e0e221d19c3c3aefaa5de68bd48f6ff2cd41e2bd877b5e78ce002476 0.600000000000 1488590 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": 1023553, "vin": [ { "gen": { "height": 1023543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5003ab63e0e221d19c3c3aefaa5de68bd48f6ff2cd41e2bd877b5e78ce002476" } } ], "extra": [ 1, 156, 37, 245, 199, 251, 66, 108, 210, 15, 166, 215, 221, 152, 39, 223, 218, 224, 192, 131, 213, 50, 107, 122, 247, 39, 112, 27, 22, 210, 187, 116, 97, 2, 17, 0, 0, 0, 2, 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