Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c8c03a429e1a913a4e9e19b3748f583ad801fbf0487f6224301b22ffce00ed

Tx prefix hash: 275b57f8a8a1fbdc72a39798dea2d895700b16925398d9fe8c87ae2b9c48030e
Tx public key: f7d118e55cfd128c4a928190a30e83de556c65ba8225d5c7e2a1f1eb263a1052
Timestamp: 1751982722 Timestamp [UCT]: 2025-07-08 13:52:02 Age [y:d:h:m:s]: 00:184:17:04:39
Block: 1321346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130531 RingCT/type: yes/0
Extra: 01f7d118e55cfd128c4a928190a30e83de556c65ba8225d5c7e2a1f1eb263a1052021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53cf61d8464daecdb4234ff94286c10abb1a28f182b1d38abe14ee47365b4510 0.600000000000 1809051 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": 1321356, "vin": [ { "gen": { "height": 1321346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53cf61d8464daecdb4234ff94286c10abb1a28f182b1d38abe14ee47365b4510" } } ], "extra": [ 1, 247, 209, 24, 229, 92, 253, 18, 140, 74, 146, 129, 144, 163, 14, 131, 222, 85, 108, 101, 186, 130, 37, 213, 199, 226, 161, 241, 235, 38, 58, 16, 82, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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