Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de62eba8e7610cf1c21063fa58a38ce9cfd5995935fd1121084408b0c595d4b

Tx prefix hash: d9d4f22f8d6ddd5dd10657e89b39f37b001bc48ecd594e447b1a869c104869e3
Tx public key: f870ac486c6c29f758e9fa858556b1885c8f0ff5595abd2e1958874cc4ba3e27
Timestamp: 1700143120 Timestamp [UCT]: 2023-11-16 13:58:40 Age [y:d:h:m:s]: 02:003:03:32:59
Block: 892930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522031 RingCT/type: yes/0
Extra: 01f870ac486c6c29f758e9fa858556b1885c8f0ff5595abd2e1958874cc4ba3e27021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.675075320000 dcy

stealth address amount amount idx
00: a1154a56f184b880fdf50271e1eba2e71ac24809db0776ebdb226b01eaa4db66 0.675075320000 1349085 of 0

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": 892940, "vin": [ { "gen": { "height": 892930 } } ], "vout": [ { "amount": 675075320, "target": { "key": "a1154a56f184b880fdf50271e1eba2e71ac24809db0776ebdb226b01eaa4db66" } } ], "extra": [ 1, 248, 112, 172, 72, 108, 108, 41, 247, 88, 233, 250, 133, 133, 86, 177, 136, 92, 143, 15, 245, 89, 90, 189, 46, 25, 88, 135, 76, 196, 186, 62, 39, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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