Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fbca6b12fdaae56c8a33995c7ed86a9e09ad1bd21b1ace3d9e2bd5ca269a98

Tx prefix hash: c22fb73c86c3e9371c5177e2cd067e247e7a7d6317866130d3c7dd1ebeb48cf0
Tx public key: 8cc039e2d5deef74e6551b0de8aea49e1c2821af80c5fbdd344fa9c316cc2e2b
Timestamp: 1697041661 Timestamp [UCT]: 2023-10-11 16:27:41 Age [y:d:h:m:s]: 01:093:02:31:48
Block: 867423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327793 RingCT/type: yes/0
Extra: 018cc039e2d5deef74e6551b0de8aea49e1c2821af80c5fbdd344fa9c316cc2e2b021100000001faf35c9c000000000000000000

1 output(s) for total of 0.820111389000 dcy

stealth address amount amount idx
00: dcdb37555b8683de10e8f638706df6315d8506800341e2f760d2601117e9d3f7 0.820111389000 1322107 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": 867433, "vin": [ { "gen": { "height": 867423 } } ], "vout": [ { "amount": 820111389, "target": { "key": "dcdb37555b8683de10e8f638706df6315d8506800341e2f760d2601117e9d3f7" } } ], "extra": [ 1, 140, 192, 57, 226, 213, 222, 239, 116, 230, 85, 27, 13, 232, 174, 164, 158, 28, 40, 33, 175, 128, 197, 251, 221, 52, 79, 169, 195, 22, 204, 46, 43, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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