Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6b56f95dd2872cc05ffdcaa1b72c9b0498269358ae480078e9818c35de8624

Tx prefix hash: 82c9642f5681e7fa0d298dac28e36a950dc0476b76980dce8ffe280b68040e1a
Tx public key: f7b39b0d7d4696fd89de23133cb154254b22ec9a840c58e52b53388e3e15d156
Timestamp: 1681495399 Timestamp [UCT]: 2023-04-14 18:03:19 Age [y:d:h:m:s]: 01:215:18:30:22
Block: 738571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415671 RingCT/type: yes/0
Extra: 01f7b39b0d7d4696fd89de23133cb154254b22ec9a840c58e52b53388e3e15d156021100000006e6d27f9c000000000000000000

1 output(s) for total of 2.191835221000 dcy

stealth address amount amount idx
00: b389218ac25f7782f383ba5d09582cddba0518d57c0b246124aec511797d8779 2.191835221000 1185290 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": 738581, "vin": [ { "gen": { "height": 738571 } } ], "vout": [ { "amount": 2191835221, "target": { "key": "b389218ac25f7782f383ba5d09582cddba0518d57c0b246124aec511797d8779" } } ], "extra": [ 1, 247, 179, 155, 13, 125, 70, 150, 253, 137, 222, 35, 19, 60, 177, 84, 37, 75, 34, 236, 154, 132, 12, 88, 229, 43, 83, 56, 142, 62, 21, 209, 86, 2, 17, 0, 0, 0, 6, 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