Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0b9f8b55c91700c68d1a80d8aaedd313769ed3566fa70ccdb497ab04209fe06

Tx prefix hash: 277a5a2d533b8edb53f2273fe665a74b04400a5581778ee68ed85ec63aad9e13
Tx public key: ead2e51c01ffe7e97fa0756a4aad33d6711ab5955dcfd8b86c4bb631d471034e
Timestamp: 1710272865 Timestamp [UCT]: 2024-03-12 19:47:45 Age [y:d:h:m:s]: 01:022:20:01:39
Block: 976922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277307 RingCT/type: yes/0
Extra: 01ead2e51c01ffe7e97fa0756a4aad33d6711ab5955dcfd8b86c4bb631d471034e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddd0a7987b59dc527bb6faeed1449d76dc6632b02c0e41ae831c0ff3b976649d 0.600000000000 1436921 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": 976932, "vin": [ { "gen": { "height": 976922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddd0a7987b59dc527bb6faeed1449d76dc6632b02c0e41ae831c0ff3b976649d" } } ], "extra": [ 1, 234, 210, 229, 28, 1, 255, 231, 233, 127, 160, 117, 106, 74, 173, 51, 214, 113, 26, 181, 149, 93, 207, 216, 184, 108, 75, 182, 49, 212, 113, 3, 78, 2, 17, 0, 0, 0, 2, 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