Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4a4eb4237a255783e509238935ad2d00f3f967dbd6c57e7066f1b804074e428

Tx prefix hash: 3a9f4c3b2deb0a8cad74d570f70450616aa9eb41b5c7d5aefc82ca3d94b76fd2
Tx public key: 1d88f7a853d44b7acd3e49993279acef682c91499d7dc4d32153c8a11295b810
Timestamp: 1715895024 Timestamp [UCT]: 2024-05-16 21:30:24 Age [y:d:h:m:s]: 01:008:15:18:46
Block: 1023530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267097 RingCT/type: yes/0
Extra: 011d88f7a853d44b7acd3e49993279acef682c91499d7dc4d32153c8a11295b8100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73b967801939d02acb7ee3d2b0ae906a6f3a0f3c3a249b4b6ed7b6641b18f4c4 0.600000000000 1488567 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": 1023540, "vin": [ { "gen": { "height": 1023530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73b967801939d02acb7ee3d2b0ae906a6f3a0f3c3a249b4b6ed7b6641b18f4c4" } } ], "extra": [ 1, 29, 136, 247, 168, 83, 212, 75, 122, 205, 62, 73, 153, 50, 121, 172, 239, 104, 44, 145, 73, 157, 125, 196, 211, 33, 83, 200, 161, 18, 149, 184, 16, 2, 17, 0, 0, 0, 1, 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