Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b70295f758de755557c077d42df1e0b349a5930cde3b90250364da6d67afdf6

Tx prefix hash: d7b895d9e868d2b4e7b44ba1c743f78870bb3c00826136856896aaf3f4a20a44
Tx public key: a7076d243bf8dfbf21e29906b31026c69e982d928e29e49ccba2b3ebde646414
Timestamp: 1733635246 Timestamp [UCT]: 2024-12-08 05:20:46 Age [y:d:h:m:s]: 00:336:14:36:20
Block: 1170499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238093 RingCT/type: yes/0
Extra: 01a7076d243bf8dfbf21e29906b31026c69e982d928e29e49ccba2b3ebde646414021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a5038c55656ee4e10c4cb2d0aacbed1960f416bc1561ea5c031e9df1790ffc 0.600000000000 1656230 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": 1170509, "vin": [ { "gen": { "height": 1170499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a5038c55656ee4e10c4cb2d0aacbed1960f416bc1561ea5c031e9df1790ffc" } } ], "extra": [ 1, 167, 7, 109, 36, 59, 248, 223, 191, 33, 226, 153, 6, 179, 16, 38, 198, 158, 152, 45, 146, 142, 41, 228, 156, 203, 162, 179, 235, 222, 100, 100, 20, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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