Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6fd4375b144a58c3ea3b9174b375f46d6faa984f0ac4f84409aef45375c8773

Tx prefix hash: f784f26b7b4665f4b1274d53020da1ba734f653c30d1b9ba5f88e281014c4d2c
Tx public key: 443448d7911e181932d38b1761f5dca7c93931e7e69541a84e9fc40f1baaa897
Timestamp: 1758952543 Timestamp [UCT]: 2025-09-27 05:55:43 Age [y:d:h:m:s]: 00:044:22:47:11
Block: 1377390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32169 RingCT/type: yes/0
Extra: 01443448d7911e181932d38b1761f5dca7c93931e7e69541a84e9fc40f1baaa8970211000000066130ce73000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75163d4b2d331f5bba44199d1feeb25d9d0560bc422a80f194a8d0a0a5f70ec5 0.600000000000 1865481 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": 1377400, "vin": [ { "gen": { "height": 1377390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75163d4b2d331f5bba44199d1feeb25d9d0560bc422a80f194a8d0a0a5f70ec5" } } ], "extra": [ 1, 68, 52, 72, 215, 145, 30, 24, 25, 50, 211, 139, 23, 97, 245, 220, 167, 201, 57, 49, 231, 230, 149, 65, 168, 78, 159, 196, 15, 27, 170, 168, 151, 2, 17, 0, 0, 0, 6, 97, 48, 206, 115, 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