Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff0174a2ddd7796c4f3329d17756bd0feb55a106c793342dacc69cb3713c0c6

Tx prefix hash: 1fd1b9e39f3fbc9fb095a0303fad15904cf13fc59ef1cc5312f620736af90bc7
Tx public key: 0f82f0f260b5fabbd6c4229b0b41acecb787360d38c24487ebae99321a95d2a6
Timestamp: 1716860644 Timestamp [UCT]: 2024-05-28 01:44:04 Age [y:d:h:m:s]: 00:305:04:17:17
Block: 1031539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218100 RingCT/type: yes/0
Extra: 010f82f0f260b5fabbd6c4229b0b41acecb787360d38c24487ebae99321a95d2a60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe69bf78da184bda6b4eb720c49e5d782e52062968afff2a1509a928a2209ee 0.600000000000 1499988 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": 1031549, "vin": [ { "gen": { "height": 1031539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe69bf78da184bda6b4eb720c49e5d782e52062968afff2a1509a928a2209ee" } } ], "extra": [ 1, 15, 130, 240, 242, 96, 181, 250, 187, 214, 196, 34, 155, 11, 65, 172, 236, 183, 135, 54, 13, 56, 194, 68, 135, 235, 174, 153, 50, 26, 149, 210, 166, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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