Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5f822c8fb97dbdac8c62e72969d31ee718a34895930d2de295377f2b502be1

Tx prefix hash: df446a84345e35915bc8e0e875fbfb101865916e78c374beedf52d79a41bb75c
Tx public key: e2ecf845fcab42eb335c578ac5dfd3c02e216b3030484323b32e09b1f177ec46
Timestamp: 1704970328 Timestamp [UCT]: 2024-01-11 10:52:08 Age [y:d:h:m:s]: 01:081:04:38:34
Block: 932937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319126 RingCT/type: yes/0
Extra: 01e2ecf845fcab42eb335c578ac5dfd3c02e216b3030484323b32e09b1f177ec460211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1069c87f81eb43a24d142ccd9b3b7bf34bd34dbd51a9d013f6a094bdcd30dd0 0.600000000000 1390877 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": 932947, "vin": [ { "gen": { "height": 932937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1069c87f81eb43a24d142ccd9b3b7bf34bd34dbd51a9d013f6a094bdcd30dd0" } } ], "extra": [ 1, 226, 236, 248, 69, 252, 171, 66, 235, 51, 92, 87, 138, 197, 223, 211, 192, 46, 33, 107, 48, 48, 72, 67, 35, 179, 46, 9, 177, 241, 119, 236, 70, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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