Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6896c670ee8235fbd2aafce4a8dcd7367390b9a53690f1b40267b14f06fb6dc

Tx prefix hash: 8df351ad327ef2f0a65b3d2f8992562625e4dca8951806af761a7f37858193d5
Tx public key: 4d9fe40422c3011eb4b740a8633dc1e5a555f8133e46e1d02828ffe477924f55
Timestamp: 1704438001 Timestamp [UCT]: 2024-01-05 07:00:01 Age [y:d:h:m:s]: 01:095:04:59:32
Block: 928519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329171 RingCT/type: yes/0
Extra: 014d9fe40422c3011eb4b740a8633dc1e5a555f8133e46e1d02828ffe477924f5502110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3308f60f3eae87927f4c17f614c54d33197b55161bc4740f604229fa8fd2b4ed 0.600000000000 1386379 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": 928529, "vin": [ { "gen": { "height": 928519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3308f60f3eae87927f4c17f614c54d33197b55161bc4740f604229fa8fd2b4ed" } } ], "extra": [ 1, 77, 159, 228, 4, 34, 195, 1, 30, 180, 183, 64, 168, 99, 61, 193, 229, 165, 85, 248, 19, 62, 70, 225, 208, 40, 40, 255, 228, 119, 146, 79, 85, 2, 17, 0, 0, 0, 12, 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