Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750db1365ce13b5c109d6491c1288f9277a11903c70056f34ed4d7375ce4fea2

Tx prefix hash: 8f7b0ac8a6c2da241fb134c3bf20e46b871305abfac399481191f55310aecbf4
Tx public key: 9e5ae2d8eea2ee2b3add346ca82fabf36bee68b24062731f83161d2316cabf4e
Timestamp: 1733621132 Timestamp [UCT]: 2024-12-08 01:25:32 Age [y:d:h:m:s]: 00:123:11:11:06
Block: 1170382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88039 RingCT/type: yes/0
Extra: 019e5ae2d8eea2ee2b3add346ca82fabf36bee68b24062731f83161d2316cabf4e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17dccdadf5455b9f981b2ce40f95959e6ef4a9b56e8795bf60c38ff9882d7eaa 0.600000000000 1656113 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": 1170392, "vin": [ { "gen": { "height": 1170382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17dccdadf5455b9f981b2ce40f95959e6ef4a9b56e8795bf60c38ff9882d7eaa" } } ], "extra": [ 1, 158, 90, 226, 216, 238, 162, 238, 43, 58, 221, 52, 108, 168, 47, 171, 243, 107, 238, 104, 178, 64, 98, 115, 31, 131, 22, 29, 35, 22, 202, 191, 78, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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