Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565be2689a430652a352fd7bb815a7cc44a5ef15aa6e59bf880bf4696432f8eb

Tx prefix hash: b63a60d943320a8af3bc92b2a529d57694ea3110836bf77c4b58d0e8bfe33e8c
Tx public key: a3200a9b713e2a174d3d3604d817371efe70a25f88e0e26c27e073b1bf3389b3
Timestamp: 1737620352 Timestamp [UCT]: 2025-01-23 08:19:12 Age [y:d:h:m:s]: 00:145:18:16:26
Block: 1203440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103916 RingCT/type: yes/0
Extra: 01a3200a9b713e2a174d3d3604d817371efe70a25f88e0e26c27e073b1bf3389b3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d579c13f8b61e89b1df0b23fb54d157e8bb23bc947b7b4eebe717966ddda50 0.600000000000 1690117 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": 1203450, "vin": [ { "gen": { "height": 1203440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d579c13f8b61e89b1df0b23fb54d157e8bb23bc947b7b4eebe717966ddda50" } } ], "extra": [ 1, 163, 32, 10, 155, 113, 62, 42, 23, 77, 61, 54, 4, 216, 23, 55, 30, 254, 112, 162, 95, 136, 224, 226, 108, 39, 224, 115, 177, 191, 51, 137, 179, 2, 17, 0, 0, 0, 3, 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