Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32cc59efb44261b45467aeaba4d09dbd88a74c197e8eda69214d46f9219fde78

Tx prefix hash: 6efe7e1ba98953111378397ce50d773b193ecbde017ac9f73cdb2cb89c81f3e5
Tx public key: 617a38933ff87381f404b82b6b4e76e7a66d73d0ac6165fe4c5601e3fc0bd1ae
Timestamp: 1730060830 Timestamp [UCT]: 2024-10-27 20:27:10 Age [y:d:h:m:s]: 00:235:09:45:36
Block: 1140928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167949 RingCT/type: yes/0
Extra: 01617a38933ff87381f404b82b6b4e76e7a66d73d0ac6165fe4c5601e3fc0bd1ae021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b59be580ffbad75c9f57db22a7c867c690b34d4d1253f708754f7dc4932c25b 0.600000000000 1624733 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": 1140938, "vin": [ { "gen": { "height": 1140928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b59be580ffbad75c9f57db22a7c867c690b34d4d1253f708754f7dc4932c25b" } } ], "extra": [ 1, 97, 122, 56, 147, 63, 248, 115, 129, 244, 4, 184, 43, 107, 78, 118, 231, 166, 109, 115, 208, 172, 97, 101, 254, 76, 86, 1, 227, 252, 11, 209, 174, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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