Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0f7dc11fb8caa030b16eb27b4aee5a3b7f265c02593eeb4358e42a640fbd0b

Tx prefix hash: 0680ff4b4ca834e7366fc6bd4eb16c2d05ebb9bac724af8996059a640cd54554
Tx public key: ce4bb4c138c5f14f3aa180a21b3686247eab2122fa72ff3cb8f9d324bf26002f
Timestamp: 1710216237 Timestamp [UCT]: 2024-03-12 04:03:57 Age [y:d:h:m:s]: 01:024:02:17:18
Block: 976458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278195 RingCT/type: yes/0
Extra: 01ce4bb4c138c5f14f3aa180a21b3686247eab2122fa72ff3cb8f9d324bf26002f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 985ebae10b440b3b86d27123d9c839d5d6b426b0137a241de766d05ec37f7882 0.600000000000 1436453 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": 976468, "vin": [ { "gen": { "height": 976458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "985ebae10b440b3b86d27123d9c839d5d6b426b0137a241de766d05ec37f7882" } } ], "extra": [ 1, 206, 75, 180, 193, 56, 197, 241, 79, 58, 161, 128, 162, 27, 54, 134, 36, 126, 171, 33, 34, 250, 114, 255, 60, 184, 249, 211, 36, 191, 38, 0, 47, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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