Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db29e447451242012df04dbd267bad4daa309a9528fd3e7c7bcbae78f75358e4

Tx prefix hash: 674398cedbfe7c5763fee410370c653cf822cbfe97d0701337cedbad40a6b3ab
Tx public key: 6ea5add4a770ccc7256e1f8b117b007e9b0db2db53364db2cd11481b5b8d812b
Timestamp: 1705999886 Timestamp [UCT]: 2024-01-23 08:51:26 Age [y:d:h:m:s]: 01:062:21:50:49
Block: 941459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306046 RingCT/type: yes/0
Extra: 016ea5add4a770ccc7256e1f8b117b007e9b0db2db53364db2cd11481b5b8d812b0211000000026127ea14000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85cf32d534c490f3c1407c9786b787f46350a6dfbcd97bdd0833f863219b984d 0.600000000000 1399609 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": 941469, "vin": [ { "gen": { "height": 941459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85cf32d534c490f3c1407c9786b787f46350a6dfbcd97bdd0833f863219b984d" } } ], "extra": [ 1, 110, 165, 173, 212, 167, 112, 204, 199, 37, 110, 31, 139, 17, 123, 0, 126, 155, 13, 178, 219, 83, 54, 77, 178, 205, 17, 72, 27, 91, 141, 129, 43, 2, 17, 0, 0, 0, 2, 97, 39, 234, 20, 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