Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5efb301f35c4af3f05e3cd137136d6c3af902ada7cc3a1c2b2a45e7ff087d4

Tx prefix hash: b8a87f6144b4ebb8589f2eef998b4606579deac00b6d8fe1d8d6d541e3e405b3
Tx public key: f43afd8b52b0a0421decccd156c7b090587ed2a822c70ed97d6db58b94973689
Timestamp: 1722625679 Timestamp [UCT]: 2024-08-02 19:07:59 Age [y:d:h:m:s]: 01:136:16:10:59
Block: 1079325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356207 RingCT/type: yes/0
Extra: 01f43afd8b52b0a0421decccd156c7b090587ed2a822c70ed97d6db58b9497368902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57bf7042684af7175a756061e77a1284dfb41482a4e557c87962a3e4351decf 0.600000000000 1552230 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": 1079335, "vin": [ { "gen": { "height": 1079325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57bf7042684af7175a756061e77a1284dfb41482a4e557c87962a3e4351decf" } } ], "extra": [ 1, 244, 58, 253, 139, 82, 176, 160, 66, 29, 236, 204, 209, 86, 199, 176, 144, 88, 126, 210, 168, 34, 199, 14, 217, 125, 109, 181, 139, 148, 151, 54, 137, 2, 17, 0, 0, 0, 10, 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