Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ae2cb85f70208290224088968b272dd8da6c2fd47a967f3f54ca4da698c3f3

Tx prefix hash: 8a8423847b1446725fe9b58d037cfdb0ad9f6f07c555aca235c99f20831fd77d
Tx public key: 4254cea95a7f3c5e82e3eacbdec6d322029f32ad35cc5c3bcb5cc3066621e4f8
Timestamp: 1710662547 Timestamp [UCT]: 2024-03-17 08:02:27 Age [y:d:h:m:s]: 01:016:18:59:36
Block: 980166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272950 RingCT/type: yes/0
Extra: 014254cea95a7f3c5e82e3eacbdec6d322029f32ad35cc5c3bcb5cc3066621e4f80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88c70d645315cdece3da7a40cb7f10d68a09ff098016a819d23047fc31e7b237 0.600000000000 1440225 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": 980176, "vin": [ { "gen": { "height": 980166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88c70d645315cdece3da7a40cb7f10d68a09ff098016a819d23047fc31e7b237" } } ], "extra": [ 1, 66, 84, 206, 169, 90, 127, 60, 94, 130, 227, 234, 203, 222, 198, 211, 34, 2, 159, 50, 173, 53, 204, 92, 59, 203, 92, 195, 6, 102, 33, 228, 248, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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