Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3417291a10b78f1436c877c01f4a34c1bb7f68cb99fc56b74f11d6aa7b8fb4

Tx prefix hash: c77137387aa29933077108ee7effbbd28613c51127bb2deb7ce4505ae4de6d3a
Tx public key: bd07c975341a555fceb21e66cfc08814cf543df0b8b4c263674926c228df31ea
Timestamp: 1734237006 Timestamp [UCT]: 2024-12-15 04:30:06 Age [y:d:h:m:s]: 00:335:21:49:18
Block: 1175495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237578 RingCT/type: yes/0
Extra: 01bd07c975341a555fceb21e66cfc08814cf543df0b8b4c263674926c228df31ea02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0726414edbb04b5b293a8cf8ea5f849b01d0bb55d880cd48ae0942043a5bede 0.600000000000 1661782 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": 1175505, "vin": [ { "gen": { "height": 1175495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0726414edbb04b5b293a8cf8ea5f849b01d0bb55d880cd48ae0942043a5bede" } } ], "extra": [ 1, 189, 7, 201, 117, 52, 26, 85, 95, 206, 178, 30, 102, 207, 192, 136, 20, 207, 84, 61, 240, 184, 180, 194, 99, 103, 73, 38, 194, 40, 223, 49, 234, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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