Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40b0b6a0c6e92abd41f6049a3c6f2bea1e67e8fc1cb6e71fc172e95f52b66fbd

Tx prefix hash: e194bf224018c792547778f8d9994c1bcb01eeb01494795051e4414fe195e360
Tx public key: 35dc49212c03101f286f578031d41fc72ec1a2e5d5d15313dc3fd96c0f784718
Timestamp: 1710473428 Timestamp [UCT]: 2024-03-15 03:30:28 Age [y:d:h:m:s]: 01:053:18:03:23
Block: 978597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299400 RingCT/type: yes/0
Extra: 0135dc49212c03101f286f578031d41fc72ec1a2e5d5d15313dc3fd96c0f78471802110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a719e4466621e732e810300ef4c06d234c8746763a79168cc0a218b959cfc3 0.600000000000 1438624 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": 978607, "vin": [ { "gen": { "height": 978597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a719e4466621e732e810300ef4c06d234c8746763a79168cc0a218b959cfc3" } } ], "extra": [ 1, 53, 220, 73, 33, 44, 3, 16, 31, 40, 111, 87, 128, 49, 212, 31, 199, 46, 193, 162, 229, 213, 209, 83, 19, 220, 63, 217, 108, 15, 120, 71, 24, 2, 17, 0, 0, 0, 14, 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