Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0ec71ae88ddc9346ec18316c837c4ccaa35ab5493b3272e3cfdbe7e440740f1

Tx prefix hash: 05a4ce9c24b58630d7d763d1dd1727d2e1db79cda3a6d95371d8f23b5b12d3f7
Tx public key: bb3454db50884aae2da38591be53b55a2a0e6fc31255fb4a778fc789ebf32fab
Timestamp: 1699096773 Timestamp [UCT]: 2023-11-04 11:19:33 Age [y:d:h:m:s]: 01:156:02:22:23
Block: 884466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372549 RingCT/type: yes/0
Extra: 01bb3454db50884aae2da38591be53b55a2a0e6fc31255fb4a778fc789ebf32fab02110000000233af99f4000000000000000000

1 output(s) for total of 0.720106927000 dcy

stealth address amount amount idx
00: 006e0eb8ecc705d9c3d10fde9053ca3e964656e94806785ee735abad38e6d99c 0.720106927000 1340209 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": 884476, "vin": [ { "gen": { "height": 884466 } } ], "vout": [ { "amount": 720106927, "target": { "key": "006e0eb8ecc705d9c3d10fde9053ca3e964656e94806785ee735abad38e6d99c" } } ], "extra": [ 1, 187, 52, 84, 219, 80, 136, 74, 174, 45, 163, 133, 145, 190, 83, 181, 90, 42, 14, 111, 195, 18, 85, 251, 74, 119, 143, 199, 137, 235, 243, 47, 171, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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