Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f24264ce640cb8481110261ef81668c342f3c06113c0bc10c5b006d734a4458

Tx prefix hash: fd5465930b9af00ba57896df33124fe58aa3bfffaea2de6619f91225cdff5469
Tx public key: c8ba7b6e49fbb557c2ac575d00ade44f6ba65dc7f2a833eea5aea8ffcae99e8c
Timestamp: 1676174607 Timestamp [UCT]: 2023-02-12 04:03:27 Age [y:d:h:m:s]: 02:101:17:35:22
Block: 695106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594352 RingCT/type: yes/0
Extra: 01c8ba7b6e49fbb557c2ac575d00ade44f6ba65dc7f2a833eea5aea8ffcae99e8c0211000000015029cbac000000000000000000

1 output(s) for total of 3.053691711000 dcy

stealth address amount amount idx
00: b647eb7fcd0dd7e326f5cede9a389b81431fa99581d37f9d36d234e03c69d8a4 3.053691711000 1138049 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": 695116, "vin": [ { "gen": { "height": 695106 } } ], "vout": [ { "amount": 3053691711, "target": { "key": "b647eb7fcd0dd7e326f5cede9a389b81431fa99581d37f9d36d234e03c69d8a4" } } ], "extra": [ 1, 200, 186, 123, 110, 73, 251, 181, 87, 194, 172, 87, 93, 0, 173, 228, 79, 107, 166, 93, 199, 242, 168, 51, 238, 165, 174, 168, 255, 202, 233, 158, 140, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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