Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d9926aa9477fdcb0c6574495cdc5d805e263ff145e1d773d8e2c0b50cdb32e

Tx prefix hash: 53e312d434db0f5b778087086f5814c158734d8d09ed60edcae61c962da24a74
Tx public key: f219c6298fed793df11191dd388e0b6462122af1784bdaed44e24fbd1ecc3a32
Timestamp: 1707667343 Timestamp [UCT]: 2024-02-11 16:02:23 Age [y:d:h:m:s]: 01:043:00:25:45
Block: 955302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291784 RingCT/type: yes/0
Extra: 01f219c6298fed793df11191dd388e0b6462122af1784bdaed44e24fbd1ecc3a3202110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38eec617b302cdd555e0b95e9af2f3cb6a8b643d535e51db71031622d066b28b 0.600000000000 1414588 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": 955312, "vin": [ { "gen": { "height": 955302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38eec617b302cdd555e0b95e9af2f3cb6a8b643d535e51db71031622d066b28b" } } ], "extra": [ 1, 242, 25, 198, 41, 143, 237, 121, 61, 241, 17, 145, 221, 56, 142, 11, 100, 98, 18, 42, 241, 120, 75, 218, 237, 68, 226, 79, 189, 30, 204, 58, 50, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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