Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8850bd73157d8319ac82c78bc74559e1f5faf9996ec125859864c2ff81bea27

Tx prefix hash: 1505d91b1ed6179dc41173c5da511b93d54cd835b893d13076725675e22319b5
Tx public key: 012b7ac9e8bda7af8459da9b80a7834fdcc46e45f0f28dc45650812052b7ddf6
Timestamp: 1703719834 Timestamp [UCT]: 2023-12-27 23:30:34 Age [y:d:h:m:s]: 01:173:11:09:18
Block: 922590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385002 RingCT/type: yes/0
Extra: 01012b7ac9e8bda7af8459da9b80a7834fdcc46e45f0f28dc45650812052b7ddf602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e2d5bc067b79c3528d8b928785fc6d0e513d9d2de7bef6349c7b3a8f71287d3 0.600000000000 1380294 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": 922600, "vin": [ { "gen": { "height": 922590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e2d5bc067b79c3528d8b928785fc6d0e513d9d2de7bef6349c7b3a8f71287d3" } } ], "extra": [ 1, 1, 43, 122, 201, 232, 189, 167, 175, 132, 89, 218, 155, 128, 167, 131, 79, 220, 196, 110, 69, 240, 242, 141, 196, 86, 80, 129, 32, 82, 183, 221, 246, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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