Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a5d2b35a4206a1eef1449662b0d7b18e1389bc0beee2b155c9f42322b525d66

Tx prefix hash: 9399aa3632135ee854cf89d4ca04340b2cc23297dda22e12cab33099f85149c7
Tx public key: a37a69434162f229f2a712a9fa5610e767d4e16ab451e54fa0b9f42a8e181a08
Timestamp: 1672619466 Timestamp [UCT]: 2023-01-02 00:31:06 Age [y:d:h:m:s]: 02:121:05:12:35
Block: 665608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608338 RingCT/type: yes/0
Extra: 01a37a69434162f229f2a712a9fa5610e767d4e16ab451e54fa0b9f42a8e181a0802110000000252542ceb000000000000000000

1 output(s) for total of 3.824409186000 dcy

stealth address amount amount idx
00: bca4e103f449028fa5898b885da023435dbe8e684ba4fe0f24cdde80cc358f65 3.824409186000 1106657 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": 665618, "vin": [ { "gen": { "height": 665608 } } ], "vout": [ { "amount": 3824409186, "target": { "key": "bca4e103f449028fa5898b885da023435dbe8e684ba4fe0f24cdde80cc358f65" } } ], "extra": [ 1, 163, 122, 105, 67, 65, 98, 242, 41, 242, 167, 18, 169, 250, 86, 16, 231, 103, 212, 225, 106, 180, 81, 229, 79, 160, 185, 244, 42, 142, 24, 26, 8, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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