Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0eed0bb66447c64147c67a2dfd11c93d5f10fe3c088ffbd06ea20652bbe0bb6

Tx prefix hash: cfdf4c1e6e21537f5f078baf98cb8c35e9aa4ab49ccc7211cc404f76e652941b
Tx public key: ec746344ad75d267960f021e795674937cb51f79ec70dcdd450ff90f9bbd738f
Timestamp: 1702730650 Timestamp [UCT]: 2023-12-16 12:44:10 Age [y:d:h:m:s]: 01:182:22:32:23
Block: 914384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391820 RingCT/type: yes/0
Extra: 01ec746344ad75d267960f021e795674937cb51f79ec70dcdd450ff90f9bbd738f02110000000afaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5bb111fcbbdba2dfd5d51e5bd6c9834892a7f7e7df6c9f0db55113f1a8e0119 0.600000000000 1371698 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": 914394, "vin": [ { "gen": { "height": 914384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5bb111fcbbdba2dfd5d51e5bd6c9834892a7f7e7df6c9f0db55113f1a8e0119" } } ], "extra": [ 1, 236, 116, 99, 68, 173, 117, 210, 103, 150, 15, 2, 30, 121, 86, 116, 147, 124, 181, 31, 121, 236, 112, 220, 221, 69, 15, 249, 15, 155, 189, 115, 143, 2, 17, 0, 0, 0, 10, 250, 243, 92, 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