Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528898a7049e2ccfbdefdc05a0b8cd0c311c0764088106f3111cced81e08be79

Tx prefix hash: 0ae651f1af0b9a0e2131e9965f7a708250a1d38a47fa18ce6df6250f4f15331c
Tx public key: 362d51e80f49d90f596783704fca1cb36857d839b4f158c7f6106c50975cbdcb
Timestamp: 1748420468 Timestamp [UCT]: 2025-05-28 08:21:08 Age [y:d:h:m:s]: 00:177:06:42:18
Block: 1292642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124378 RingCT/type: yes/0
Extra: 01362d51e80f49d90f596783704fca1cb36857d839b4f158c7f6106c50975cbdcb021100000008523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e80eb5a92245d567eaea07bcd739f8b6b8ecc436c295e0233d1f30444cc779f 0.600000000000 1780113 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": 1292652, "vin": [ { "gen": { "height": 1292642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e80eb5a92245d567eaea07bcd739f8b6b8ecc436c295e0233d1f30444cc779f" } } ], "extra": [ 1, 54, 45, 81, 232, 15, 73, 217, 15, 89, 103, 131, 112, 79, 202, 28, 179, 104, 87, 216, 57, 180, 241, 88, 199, 246, 16, 108, 80, 151, 92, 189, 203, 2, 17, 0, 0, 0, 8, 82, 53, 96, 218, 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