Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e254c23f41a1d341ca1bd5d802f70d13f249372ca4ca929eccb6ef40541cadeb

Tx prefix hash: 3c45542cf2416014ee2a6e5573242a7343e7fba105f0af0a448666eef6d9521c
Tx public key: d9a933a04f69a613862ab1b0e53f68dff9d50df03a1932ed1ec4650de3cf5752
Timestamp: 1702101813 Timestamp [UCT]: 2023-12-09 06:03:33 Age [y:d:h:m:s]: 01:121:12:21:21
Block: 909166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347989 RingCT/type: yes/0
Extra: 01d9a933a04f69a613862ab1b0e53f68dff9d50df03a1932ed1ec4650de3cf575202110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea93ffea3a90c61ebc7fa95cdc47add0d3f78195fa1e7822cfba287122b1253 0.600000000000 1366235 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": 909176, "vin": [ { "gen": { "height": 909166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea93ffea3a90c61ebc7fa95cdc47add0d3f78195fa1e7822cfba287122b1253" } } ], "extra": [ 1, 217, 169, 51, 160, 79, 105, 166, 19, 134, 42, 177, 176, 229, 63, 104, 223, 249, 213, 13, 240, 58, 25, 50, 237, 30, 196, 101, 13, 227, 207, 87, 82, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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