Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a683c20d664672a6f5b3d69f7589950a3cde753060c1b698cc67713d8f1a9866

Tx prefix hash: b7a9b34cf3a741944abc17ac8719c357f2d5132b4efbff3a29e9bc0be972dc41
Tx public key: 7885c8424617ed80c98ccbe718cd4f63268f098ea6e6bd7354fc22dfaf4b28e3
Timestamp: 1716839294 Timestamp [UCT]: 2024-05-27 19:48:14 Age [y:d:h:m:s]: 00:313:06:43:44
Block: 1031361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223893 RingCT/type: yes/0
Extra: 017885c8424617ed80c98ccbe718cd4f63268f098ea6e6bd7354fc22dfaf4b28e30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b2cdd487e36e2bc1357a018db9276c7821430945e4ac6c8c32ef8b8ad68258a 0.600000000000 1499794 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": 1031371, "vin": [ { "gen": { "height": 1031361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b2cdd487e36e2bc1357a018db9276c7821430945e4ac6c8c32ef8b8ad68258a" } } ], "extra": [ 1, 120, 133, 200, 66, 70, 23, 237, 128, 201, 140, 203, 231, 24, 205, 79, 99, 38, 143, 9, 142, 166, 230, 189, 115, 84, 252, 34, 223, 175, 75, 40, 227, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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