Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e16a0cabbeb625d72e8b3e066420327cf5fb57ae586fc929d67e69ad653e2d

Tx prefix hash: 45ea91b2d8934cbda3d44c4a08c85d40a9313eacaa0bc162d44e6398abc98488
Tx public key: db67afc720a5b87d2f7b5f7758b4e5642dade50f14f59e824670c4744fbd63ed
Timestamp: 1703171719 Timestamp [UCT]: 2023-12-21 15:15:19 Age [y:d:h:m:s]: 01:024:18:58:32
Block: 918040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279066 RingCT/type: yes/0
Extra: 01db67afc720a5b87d2f7b5f7758b4e5642dade50f14f59e824670c4744fbd63ed0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f3fd27d0f62ab3b946d81ca176f02376118d308ef2862e691b5272b156df0a1 0.600000000000 1375676 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": 918050, "vin": [ { "gen": { "height": 918040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f3fd27d0f62ab3b946d81ca176f02376118d308ef2862e691b5272b156df0a1" } } ], "extra": [ 1, 219, 103, 175, 199, 32, 165, 184, 125, 47, 123, 95, 119, 88, 180, 229, 100, 45, 173, 229, 15, 20, 245, 158, 130, 70, 112, 196, 116, 79, 189, 99, 237, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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