Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f1ed302134c73bcfee23ea662b7412762bbd4e03c0939e8cf81a38a5e7b2fa

Tx prefix hash: 30d239e4f8a9f6ff81e31238c9918535051b1f66c9a158fa82fd039f910e94dd
Tx public key: bb1ee5fad725054e446fa7fa87f7f6c9ebfb56cfe91ff6abecf2288e7aed851c
Timestamp: 1676440705 Timestamp [UCT]: 2023-02-15 05:58:25 Age [y:d:h:m:s]: 02:011:01:44:27
Block: 697306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529476 RingCT/type: yes/0
Extra: 01bb1ee5fad725054e446fa7fa87f7f6c9ebfb56cfe91ff6abecf2288e7aed851c021100000003faf35c9c000000000000000000

1 output(s) for total of 3.002864071000 dcy

stealth address amount amount idx
00: cc5d6de15e220cdb8a31f7edd60fb259311d9f9c53f0dd1a0afe4c4809b7cace 3.002864071000 1140449 of 0

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": 697316, "vin": [ { "gen": { "height": 697306 } } ], "vout": [ { "amount": 3002864071, "target": { "key": "cc5d6de15e220cdb8a31f7edd60fb259311d9f9c53f0dd1a0afe4c4809b7cace" } } ], "extra": [ 1, 187, 30, 229, 250, 215, 37, 5, 78, 68, 111, 167, 250, 135, 247, 246, 201, 235, 251, 86, 207, 233, 31, 246, 171, 236, 242, 40, 142, 122, 237, 133, 28, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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