Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead7b67c4c8f8ecfd941fdadf5cf92dd08ea2c3cefb0fa2c720155e14159f627

Tx prefix hash: 941ae3eb47ae62794565d6bbdb0ed207d09b3690b88092527d6b0cda9a6516e8
Tx public key: 77bff2e4be54ba12e6cd3a04f99fc66ad19f282781b2110ae2e1eee22e1e5d67
Timestamp: 1696709193 Timestamp [UCT]: 2023-10-07 20:06:33 Age [y:d:h:m:s]: 02:030:10:59:47
Block: 864660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541384 RingCT/type: yes/0
Extra: 0177bff2e4be54ba12e6cd3a04f99fc66ad19f282781b2110ae2e1eee22e1e5d67021100000001bfa22221000000000000000000

1 output(s) for total of 0.837572708000 dcy

stealth address amount amount idx
00: 5ec6cca8d2b79cc7a03e5985c890fdafb892ac48e4ee4c79733a3424f0553104 0.837572708000 1319180 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": 864670, "vin": [ { "gen": { "height": 864660 } } ], "vout": [ { "amount": 837572708, "target": { "key": "5ec6cca8d2b79cc7a03e5985c890fdafb892ac48e4ee4c79733a3424f0553104" } } ], "extra": [ 1, 119, 191, 242, 228, 190, 84, 186, 18, 230, 205, 58, 4, 249, 159, 198, 106, 209, 159, 40, 39, 129, 178, 17, 10, 226, 225, 238, 226, 46, 30, 93, 103, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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