Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a76d1f91ea2d873777ad7983e7fe577bd003bd847ec9f18b1893062d3aa44e

Tx prefix hash: 0ed51f4f868a6e82cd9ae085ee5f9f9640c33bb6bd57e880904851be30248b60
Tx public key: 8fa2a74052ff0676af5d0d9af37c9eb8fa6dc04ded60ce9a81bc8f9a09fb54c3
Timestamp: 1722407960 Timestamp [UCT]: 2024-07-31 06:39:20 Age [y:d:h:m:s]: 01:099:04:33:28
Block: 1077516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329377 RingCT/type: yes/0
Extra: 018fa2a74052ff0676af5d0d9af37c9eb8fa6dc04ded60ce9a81bc8f9a09fb54c302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 640a1ffd517b9fcbae29d16375ae194486a13fe1892fb80d641c34998ee05f65 0.600000000000 1550067 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": 1077526, "vin": [ { "gen": { "height": 1077516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "640a1ffd517b9fcbae29d16375ae194486a13fe1892fb80d641c34998ee05f65" } } ], "extra": [ 1, 143, 162, 167, 64, 82, 255, 6, 118, 175, 93, 13, 154, 243, 124, 158, 184, 250, 109, 192, 77, 237, 96, 206, 154, 129, 188, 143, 154, 9, 251, 84, 195, 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