Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47bc2f6f27a16bd3671089a2b05289adadb8139be261b7ea8240e5b093999fe

Tx prefix hash: c117101a451bd9024df8bc5cc5dd268ee8df8d587895d1da5d8f422efe3403d1
Tx public key: de1e7d1b1f7fe930aff506f038646accf8e6184c57949aa95809579ea742694c
Timestamp: 1744847710 Timestamp [UCT]: 2025-04-16 23:55:10 Age [y:d:h:m:s]: 00:290:09:56:25
Block: 1263045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205203 RingCT/type: yes/0
Extra: 01de1e7d1b1f7fe930aff506f038646accf8e6184c57949aa95809579ea742694c021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b51f7d386cf90f6d4704c0a566dcfda69d7a0381417b85251b3a272ad7bd657 0.600000000000 1750228 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": 1263055, "vin": [ { "gen": { "height": 1263045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b51f7d386cf90f6d4704c0a566dcfda69d7a0381417b85251b3a272ad7bd657" } } ], "extra": [ 1, 222, 30, 125, 27, 31, 127, 233, 48, 175, 245, 6, 240, 56, 100, 106, 204, 248, 230, 24, 76, 87, 148, 154, 169, 88, 9, 87, 158, 167, 66, 105, 76, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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