Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36e9146bb31dafd3331addc3b3999361f9fd3a7141d289f72ebadeba44688c9

Tx prefix hash: cf17043ffaf95c0cfbb0b1990bca378eb48cefcd815fcd1d2fe9a97e56260b29
Tx public key: 2c80d5d7de65eda2918ce237a8f79340bdaf3d6e036da00afa3595a2206e0b38
Timestamp: 1714134457 Timestamp [UCT]: 2024-04-26 12:27:37 Age [y:d:h:m:s]: 00:202:22:25:06
Block: 1008926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145271 RingCT/type: yes/0
Extra: 012c80d5d7de65eda2918ce237a8f79340bdaf3d6e036da00afa3595a2206e0b3802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: e9d2df7eef9ea688a4c64d8127c0a4686d8f3b4f06014fbb3612cb39bc155990 0.600010000000 1470440 of 0

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": 1008936, "vin": [ { "gen": { "height": 1008926 } } ], "vout": [ { "amount": 600010000, "target": { "key": "e9d2df7eef9ea688a4c64d8127c0a4686d8f3b4f06014fbb3612cb39bc155990" } } ], "extra": [ 1, 44, 128, 213, 215, 222, 101, 237, 162, 145, 140, 226, 55, 168, 247, 147, 64, 189, 175, 61, 110, 3, 109, 160, 10, 250, 53, 149, 162, 32, 110, 11, 56, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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