Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786c8d8c9f7c1765225fc3bc556720ed282b14b2587f1d4496235b667d7fb657

Tx prefix hash: ddb2df190c6aa40091853f85ea50bb25cb4764a781b09d21aa88ca71fb24e98c
Tx public key: 7c3bb63d3f75b8c1e1146210e111da5e4979d6770fbd52004d5218634f095df3
Timestamp: 1699389858 Timestamp [UCT]: 2023-11-07 20:44:18 Age [y:d:h:m:s]: 01:210:18:33:24
Block: 886691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411886 RingCT/type: yes/0
Extra: 017c3bb63d3f75b8c1e1146210e111da5e4979d6770fbd52004d5218634f095df302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.707985946000 dcy

stealth address amount amount idx
00: 31edc110a64a3e01639f8d7f897b3d1cff5b5b3f89dcf88d696f181083de4f2e 0.707985946000 1342526 of 0

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": 886701, "vin": [ { "gen": { "height": 886691 } } ], "vout": [ { "amount": 707985946, "target": { "key": "31edc110a64a3e01639f8d7f897b3d1cff5b5b3f89dcf88d696f181083de4f2e" } } ], "extra": [ 1, 124, 59, 182, 61, 63, 117, 184, 193, 225, 20, 98, 16, 225, 17, 218, 94, 73, 121, 214, 119, 15, 189, 82, 0, 77, 82, 24, 99, 79, 9, 93, 243, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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