Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361f1a11dcc27de2c168ea7c422463d9b61478c4498ce0ba6b5f42e65a15032a

Tx prefix hash: 84b1b8254b2a3526d369aec25d5ccca0781f430aff9dc844ba95aa8dff274d47
Tx public key: 952f6c56b3e9fea065744211c8fd66f103c15551d202f9f1cfdaa2ffea04c359
Timestamp: 1709278083 Timestamp [UCT]: 2024-03-01 07:28:03 Age [y:d:h:m:s]: 01:013:17:17:24
Block: 968674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270812 RingCT/type: yes/0
Extra: 01952f6c56b3e9fea065744211c8fd66f103c15551d202f9f1cfdaa2ffea04c3590211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 853d88a8fb94a034ff007002c9ef7f3b587f1650670924419bef8cc6ef0a56c7 0.600000000000 1428491 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": 968684, "vin": [ { "gen": { "height": 968674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "853d88a8fb94a034ff007002c9ef7f3b587f1650670924419bef8cc6ef0a56c7" } } ], "extra": [ 1, 149, 47, 108, 86, 179, 233, 254, 160, 101, 116, 66, 17, 200, 253, 102, 241, 3, 193, 85, 81, 210, 2, 249, 241, 207, 218, 162, 255, 234, 4, 195, 89, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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