Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03b415bdcc1a3950f5ac24d2de4fe64f47ed11d3203df4b7bb4c4904c519b9e

Tx prefix hash: be2db6d6a99e70a98c3d5e606779728574d97aed62c6608cd97ab05273aa2ede
Tx public key: 6c454d272b1d917a94fe43990d9374e16e82630db79867045c21fe72f7c14843
Timestamp: 1766203349 Timestamp [UCT]: 2025-12-20 04:02:29 Age [y:d:h:m:s]: 00:002:06:36:25
Block: 1437473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1618 RingCT/type: yes/0
Extra: 016c454d272b1d917a94fe43990d9374e16e82630db79867045c21fe72f7c14843021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc9ff4db4e80058b004e69d25d47e10fd150c710ea15c6f684dc7b9df430572c 0.600000000000 1926282 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": 1437483, "vin": [ { "gen": { "height": 1437473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc9ff4db4e80058b004e69d25d47e10fd150c710ea15c6f684dc7b9df430572c" } } ], "extra": [ 1, 108, 69, 77, 39, 43, 29, 145, 122, 148, 254, 67, 153, 13, 147, 116, 225, 110, 130, 99, 13, 183, 152, 103, 4, 92, 33, 254, 114, 247, 193, 72, 67, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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