Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9693bb1c7ca0f4413286e592ae7c87482c738aa84304499f5b41e9863749327b

Tx prefix hash: 9c64e39e2132d329ea816fa9b0ca3ad1511026084c531afe1377d402c5636f73
Tx public key: bb2ab3ba4d897ee4f3f00ada83e773fecbbf0a21a74a2bf3751cd433c07ec5d8
Timestamp: 1722811002 Timestamp [UCT]: 2024-08-04 22:36:42 Age [y:d:h:m:s]: 00:262:17:32:54
Block: 1080856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187682 RingCT/type: yes/0
Extra: 01bb2ab3ba4d897ee4f3f00ada83e773fecbbf0a21a74a2bf3751cd433c07ec5d802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa8f3c2639b813bc223d4f617f22afebf59bae098a90cc649824d92efbfead3 0.600000000000 1554375 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": 1080866, "vin": [ { "gen": { "height": 1080856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa8f3c2639b813bc223d4f617f22afebf59bae098a90cc649824d92efbfead3" } } ], "extra": [ 1, 187, 42, 179, 186, 77, 137, 126, 228, 243, 240, 10, 218, 131, 231, 115, 254, 203, 191, 10, 33, 167, 74, 43, 243, 117, 28, 212, 51, 192, 126, 197, 216, 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