Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dc42f27607d3a389b23335d44e9f9e9c2c5bb3f3705cbcada1e30ec76a8ea38

Tx prefix hash: d4f8f55142a4874a15c7db647a1ff4d7355447e42a1069629bc9e6c245c45086
Tx public key: 0b18a2fef98fcc89d13e498b3a23bb22b14286292a0daddaaaae3b4ea7309e92
Timestamp: 1755088311 Timestamp [UCT]: 2025-08-13 12:31:51 Age [y:d:h:m:s]: 00:008:06:49:20
Block: 1346062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5417 RingCT/type: yes/0
Extra: 010b18a2fef98fcc89d13e498b3a23bb22b14286292a0daddaaaae3b4ea7309e92021100000011b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443223ef981ff82e3eee118cc2831e6db76a1c83255bbdf40ea16b22c58fc582 0.600000000000 1833959 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": 1346072, "vin": [ { "gen": { "height": 1346062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443223ef981ff82e3eee118cc2831e6db76a1c83255bbdf40ea16b22c58fc582" } } ], "extra": [ 1, 11, 24, 162, 254, 249, 143, 204, 137, 209, 62, 73, 139, 58, 35, 187, 34, 177, 66, 134, 41, 42, 13, 173, 218, 170, 174, 59, 78, 167, 48, 158, 146, 2, 17, 0, 0, 0, 17, 178, 247, 132, 196, 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