Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578e72a57215c8747ef7347c6073e3b8cdc7f4a63db09528d9eec206acb5d42e

Tx prefix hash: 558848c914144d05702b0c685f5c6a2854833bc6ba46ce03bebe917b3dcc5086
Tx public key: f815dc2d6f126e4b8e9e3205cc8629ff287268ee08ec93b92e550638709b5ae2
Timestamp: 1706215039 Timestamp [UCT]: 2024-01-25 20:37:19 Age [y:d:h:m:s]: 01:030:14:26:36
Block: 943238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282941 RingCT/type: yes/0
Extra: 01f815dc2d6f126e4b8e9e3205cc8629ff287268ee08ec93b92e550638709b5ae202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e52c1ab129e7787f7e12e656d5ba517aa0a46c60c37c9667ff1f48b3a486dac2 0.600000000000 1401438 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": 943248, "vin": [ { "gen": { "height": 943238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e52c1ab129e7787f7e12e656d5ba517aa0a46c60c37c9667ff1f48b3a486dac2" } } ], "extra": [ 1, 248, 21, 220, 45, 111, 18, 110, 75, 142, 158, 50, 5, 204, 134, 41, 255, 40, 114, 104, 238, 8, 236, 147, 185, 46, 85, 6, 56, 112, 155, 90, 226, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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