Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7742e0acc6650444ef993e7f2f1069f92f028c7c82c84f5f36f972d4858cd53c

Tx prefix hash: 23c8f4fc7826e550160c2d01a9a8f603e0ec27a075d229442fdc2bd586f42653
Tx public key: a1e5f5b78c81a52ad5cf2ad2251bbc918142ac1154437c8297a9aaf138afaf9f
Timestamp: 1706905307 Timestamp [UCT]: 2024-02-02 20:21:47 Age [y:d:h:m:s]: 01:271:06:25:18
Block: 948976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452663 RingCT/type: yes/0
Extra: 01a1e5f5b78c81a52ad5cf2ad2251bbc918142ac1154437c8297a9aaf138afaf9f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a963b042bc43ac8b0d6a389390a4532276e55ce341be2f074e80e2cf298fda1e 0.600000000000 1407496 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": 948986, "vin": [ { "gen": { "height": 948976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a963b042bc43ac8b0d6a389390a4532276e55ce341be2f074e80e2cf298fda1e" } } ], "extra": [ 1, 161, 229, 245, 183, 140, 129, 165, 42, 213, 207, 42, 210, 37, 27, 188, 145, 129, 66, 172, 17, 84, 67, 124, 130, 151, 169, 170, 241, 56, 175, 175, 159, 2, 17, 0, 0, 0, 8, 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