Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01b866e7aa3ad64d5054fc7e0bbd0e21cd4e4eeedb888a5cbd2f22e4763760d3

Tx prefix hash: 7c7754880d226835825dc06d154f9b64d70c0018796e3be8b6826937a00e4411
Tx public key: 11fd1a2ca95082e9cea0546452a80bfe7add96469a49b76b01cc81f44614ba8a
Timestamp: 1697277441 Timestamp [UCT]: 2023-10-14 09:57:21 Age [y:d:h:m:s]: 01:142:01:33:01
Block: 869381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362540 RingCT/type: yes/0
Extra: 0111fd1a2ca95082e9cea0546452a80bfe7add96469a49b76b01cc81f44614ba8a02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.807941429000 dcy

stealth address amount amount idx
00: 445e6e7b2b80e461dbf01c6772199956829629a4c88c196ae96f1f30f01f92d1 0.807941429000 1324226 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": 869391, "vin": [ { "gen": { "height": 869381 } } ], "vout": [ { "amount": 807941429, "target": { "key": "445e6e7b2b80e461dbf01c6772199956829629a4c88c196ae96f1f30f01f92d1" } } ], "extra": [ 1, 17, 253, 26, 44, 169, 80, 130, 233, 206, 160, 84, 100, 82, 168, 11, 254, 122, 221, 150, 70, 154, 73, 183, 107, 1, 204, 129, 244, 70, 20, 186, 138, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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