Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53cab5f62a033c84ca2436975ad3adc8a20425c8d0ffa8e9923f84319ff7e36

Tx prefix hash: b6a2c8d87a54b3ed72196c9294e4ba422d4efbd2273cf40ca650ac0560ef2af2
Tx public key: a5358ba7df5daa536dee93b3940ee055fd872f6a110f1ed377ab3c6dfff9f06d
Timestamp: 1711858737 Timestamp [UCT]: 2024-03-31 04:18:57 Age [y:d:h:m:s]: 01:267:07:32:18
Block: 990084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449751 RingCT/type: yes/0
Extra: 01a5358ba7df5daa536dee93b3940ee055fd872f6a110f1ed377ab3c6dfff9f06d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4289a6b520dd3827f3a9372e1ad84977a0c7643e3432e26aa08e830d9221104d 0.600000000000 1450406 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": 990094, "vin": [ { "gen": { "height": 990084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4289a6b520dd3827f3a9372e1ad84977a0c7643e3432e26aa08e830d9221104d" } } ], "extra": [ 1, 165, 53, 139, 167, 223, 93, 170, 83, 109, 238, 147, 179, 148, 14, 224, 85, 253, 135, 47, 106, 17, 15, 30, 211, 119, 171, 60, 109, 255, 249, 240, 109, 2, 17, 0, 0, 0, 4, 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