Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ef17b6252d685e3fdd81a4965b343894c65c761f4b9ae26e11c221764e5ea4

Tx prefix hash: d87c7f37b03511fb71449c48019ca10071d63fc2f1c296383a2844dfd86f83bd
Tx public key: 0134157f38da50d8ed2719153b8e687097157adc41e0d37bf13d82f38c51c28c
Timestamp: 1737025314 Timestamp [UCT]: 2025-01-16 11:01:54 Age [y:d:h:m:s]: 00:152:01:25:03
Block: 1198550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108404 RingCT/type: yes/0
Extra: 010134157f38da50d8ed2719153b8e687097157adc41e0d37bf13d82f38c51c28c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bb7dc329d7bdf6e0b0770c51ff1cc8fae924378cb42543f1d85a08df73b2f41 0.600000000000 1685175 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": 1198560, "vin": [ { "gen": { "height": 1198550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb7dc329d7bdf6e0b0770c51ff1cc8fae924378cb42543f1d85a08df73b2f41" } } ], "extra": [ 1, 1, 52, 21, 127, 56, 218, 80, 216, 237, 39, 25, 21, 59, 142, 104, 112, 151, 21, 122, 220, 65, 224, 211, 123, 241, 61, 130, 243, 140, 81, 194, 140, 2, 17, 0, 0, 0, 1, 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