Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0b8fd122e61be88d05c69800aa8ab604f399e7099b8a96d473e6de89baf1e0

Tx prefix hash: d14628c40cccf0662650dbeb17df083898d81bc5a13dfbe0fc3c9b7111a649dc
Tx public key: 9668cf5a771ec78b637f1d5f31a646beb2fc388371b0f892a506d1b0de59549c
Timestamp: 1728487037 Timestamp [UCT]: 2024-10-09 15:17:17 Age [y:d:h:m:s]: 00:167:17:40:27
Block: 1127920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119650 RingCT/type: yes/0
Extra: 019668cf5a771ec78b637f1d5f31a646beb2fc388371b0f892a506d1b0de59549c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ec7700b6bc83bf8c46dc4c1bc8ebbbe6ef108576894910f12f10fadd4addd8d 0.600000000000 1610733 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": 1127930, "vin": [ { "gen": { "height": 1127920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec7700b6bc83bf8c46dc4c1bc8ebbbe6ef108576894910f12f10fadd4addd8d" } } ], "extra": [ 1, 150, 104, 207, 90, 119, 30, 199, 139, 99, 127, 29, 95, 49, 166, 70, 190, 178, 252, 56, 131, 113, 176, 248, 146, 165, 6, 209, 176, 222, 89, 84, 156, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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