Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76da6f8a89022e45af893a2a833abc817f09bb140a7b4cd41ad90030de5a7d17

Tx prefix hash: 8fe0f8a6ad0367f97a5df2c8a568af712bf2f48832b89b64374b8379ddf65549
Tx public key: ac91e7ee8b6f09334f480f7d33b446f98136968a38c4e725899f502f797d0d5b
Timestamp: 1716982893 Timestamp [UCT]: 2024-05-29 11:41:33 Age [y:d:h:m:s]: 01:175:22:42:29
Block: 1032548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384336 RingCT/type: yes/0
Extra: 01ac91e7ee8b6f09334f480f7d33b446f98136968a38c4e725899f502f797d0d5b02110000000941ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86949b97e4e9608508f21517e641007c05d0d1f609cc30e37ad9a0e7efb1f960 0.600000000000 1501001 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": 1032558, "vin": [ { "gen": { "height": 1032548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86949b97e4e9608508f21517e641007c05d0d1f609cc30e37ad9a0e7efb1f960" } } ], "extra": [ 1, 172, 145, 231, 238, 139, 111, 9, 51, 79, 72, 15, 125, 51, 180, 70, 249, 129, 54, 150, 138, 56, 196, 231, 37, 137, 159, 80, 47, 121, 125, 13, 91, 2, 17, 0, 0, 0, 9, 65, 238, 28, 155, 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