Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ab6c5efa8cabe8f3d74d80d0aa2a359735a8583c1947247cc5e82daad833a9

Tx prefix hash: 3687617db4c8c81ab148823b03eb7e961b61562cdafbe0cebe9c8f8b4770eca9
Tx public key: 4c0ee6c221c57dfd54a684f70c9d0d67a8a23060d50c8c432f1379c013126c6c
Timestamp: 1702163047 Timestamp [UCT]: 2023-12-09 23:04:07 Age [y:d:h:m:s]: 01:333:19:48:12
Block: 909683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497436 RingCT/type: yes/0
Extra: 014c0ee6c221c57dfd54a684f70c9d0d67a8a23060d50c8c432f1379c013126c6c0211000000024b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9961e02e623737314bc57dccaf1540877a996f1bb5f6d4c1a8dced2c8c4ca208 0.600000000000 1366788 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": 909693, "vin": [ { "gen": { "height": 909683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9961e02e623737314bc57dccaf1540877a996f1bb5f6d4c1a8dced2c8c4ca208" } } ], "extra": [ 1, 76, 14, 230, 194, 33, 197, 125, 253, 84, 166, 132, 247, 12, 157, 13, 103, 168, 162, 48, 96, 213, 12, 140, 67, 47, 19, 121, 192, 19, 18, 108, 108, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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