Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9e92f244dc08e74020f105bb8269118e47e089cbc79b3712046e574fbf13b7

Tx prefix hash: e6e639a5a291ae0e982d6e2dc09f470f4d363b69a8a14ef1376d5e35b577777a
Tx public key: 5cb63a9b9e0e7dfc28fb3765aa67acd00c3c172dac570dc9e1d151813e037f10
Timestamp: 1724796619 Timestamp [UCT]: 2024-08-27 22:10:19 Age [y:d:h:m:s]: 01:157:11:26:07
Block: 1097307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370931 RingCT/type: yes/0
Extra: 015cb63a9b9e0e7dfc28fb3765aa67acd00c3c172dac570dc9e1d151813e037f10021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e635f3b9eeb702b42fb78a2ffd223ca250ad2ca53d1e7922afcbcc55ce9b21c 0.600000000000 1572684 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": 1097317, "vin": [ { "gen": { "height": 1097307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e635f3b9eeb702b42fb78a2ffd223ca250ad2ca53d1e7922afcbcc55ce9b21c" } } ], "extra": [ 1, 92, 182, 58, 155, 158, 14, 125, 252, 40, 251, 55, 101, 170, 103, 172, 208, 12, 60, 23, 45, 172, 87, 13, 201, 225, 209, 81, 129, 62, 3, 127, 16, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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