Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0268c5e3c96aa423af3e2391deeb7669c9158bab9d8153e294adda7256f2b12b

Tx prefix hash: 040943bd0f64d16fec72d4dbe31cbe7faa8b5e0c9eb503123c228334573177df
Tx public key: 206f8eba04ca2fc376e7dc177cbdd4c7179ed293ab1f65b587a884d2d5685a49
Timestamp: 1682804666 Timestamp [UCT]: 2023-04-29 21:44:26 Age [y:d:h:m:s]: 01:265:20:02:33
Block: 749440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451432 RingCT/type: yes/0
Extra: 01206f8eba04ca2fc376e7dc177cbdd4c7179ed293ab1f65b587a884d2d5685a4902110000000233af99f4000000000000000000

1 output(s) for total of 2.017410963000 dcy

stealth address amount amount idx
00: 7c740c992b728e875a292aa6b5f48ce23933d012170962d941d025b21d49cadd 2.017410963000 1197411 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": 749450, "vin": [ { "gen": { "height": 749440 } } ], "vout": [ { "amount": 2017410963, "target": { "key": "7c740c992b728e875a292aa6b5f48ce23933d012170962d941d025b21d49cadd" } } ], "extra": [ 1, 32, 111, 142, 186, 4, 202, 47, 195, 118, 231, 220, 23, 124, 189, 212, 199, 23, 158, 210, 147, 171, 31, 101, 181, 135, 168, 132, 210, 213, 104, 90, 73, 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