Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9424826be28fbf41d6479d67cadccbbcfe54e21f2a19eddf0ba92c9e615008d5

Tx prefix hash: 65a87818df68e5a941c322a7018be96c3b3860b12a54475d2bc303b0fa95cd1d
Tx public key: e82805e3239d1ca4948f9aad2cdf51403dbe929620873bfd9ab40e86d32097b0
Timestamp: 1632157091 Timestamp [UCT]: 2021-09-20 16:58:11 Age [y:d:h:m:s]: 03:049:08:45:19
Block: 337660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811251 RingCT/type: yes/0
Extra: 01e82805e3239d1ca4948f9aad2cdf51403dbe929620873bfd9ab40e86d32097b0021100000032fdc024ec000000000000000000

1 output(s) for total of 46.686647203000 dcy

stealth address amount amount idx
00: bfdbbf4893a0239e2a1b51c02a8d0fc900ce4ffc7ad9fff222a896ada11aa9f7 46.686647203000 695201 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": 337670, "vin": [ { "gen": { "height": 337660 } } ], "vout": [ { "amount": 46686647203, "target": { "key": "bfdbbf4893a0239e2a1b51c02a8d0fc900ce4ffc7ad9fff222a896ada11aa9f7" } } ], "extra": [ 1, 232, 40, 5, 227, 35, 157, 28, 164, 148, 143, 154, 173, 44, 223, 81, 64, 61, 190, 146, 150, 32, 135, 59, 253, 154, 180, 14, 134, 211, 32, 151, 176, 2, 17, 0, 0, 0, 50, 253, 192, 36, 236, 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