Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b0c602716465839639399f653d6a234926a3c3394feba9ad548af65f4fbce40

Tx prefix hash: 620bc25b4d60cb2af2b90b2e3a79e4de91ba660927a4c85f56715f29fd9e8e50
Tx public key: e11d23661769be05329f6d0f51e31a5a84027651f99d8063673169a80c069f01
Timestamp: 1737280572 Timestamp [UCT]: 2025-01-19 09:56:12 Age [y:d:h:m:s]: 00:335:22:52:19
Block: 1200632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237694 RingCT/type: yes/0
Extra: 01e11d23661769be05329f6d0f51e31a5a84027651f99d8063673169a80c069f01021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4ebc666353e4f645496fdc39f01d92a4ff09973db253cdc9229d4f4c711fb7 0.600000000000 1687277 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": 1200642, "vin": [ { "gen": { "height": 1200632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4ebc666353e4f645496fdc39f01d92a4ff09973db253cdc9229d4f4c711fb7" } } ], "extra": [ 1, 225, 29, 35, 102, 23, 105, 190, 5, 50, 159, 109, 15, 81, 227, 26, 90, 132, 2, 118, 81, 249, 157, 128, 99, 103, 49, 105, 168, 12, 6, 159, 1, 2, 17, 0, 0, 0, 7, 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