Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baacf527b35269058a842b1270e5041a81de635746ca1845ca75167aed6e95d1

Tx prefix hash: bb5b6c636d9c4f8769ea58b1558987ee99a26133788dee1ae0c35f6ffd76358c
Tx public key: 80152cc94cea7c7d7d91cbc7a664a3cf6629e5eb55ffb5f654f83e5da6ab0b75
Timestamp: 1718824114 Timestamp [UCT]: 2024-06-19 19:08:34 Age [y:d:h:m:s]: 01:160:08:16:35
Block: 1047802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373180 RingCT/type: yes/0
Extra: 0180152cc94cea7c7d7d91cbc7a664a3cf6629e5eb55ffb5f654f83e5da6ab0b750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b2082e9a95369ccc8d556219f0e13b43138232ee1c77adea3127a4d6a481f6 0.600000000000 1517721 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": 1047812, "vin": [ { "gen": { "height": 1047802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b2082e9a95369ccc8d556219f0e13b43138232ee1c77adea3127a4d6a481f6" } } ], "extra": [ 1, 128, 21, 44, 201, 76, 234, 124, 125, 125, 145, 203, 199, 166, 100, 163, 207, 102, 41, 229, 235, 85, 255, 181, 246, 84, 248, 62, 93, 166, 171, 11, 117, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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