Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b8a2c800245590b62eac083f641b6b592d2a9dd1df5fbbbd7f3cc89a38b49d

Tx prefix hash: bf48d1910367f2e76961cc5f5a4fd5f104185c2ad71a6c21682ac97c7eb2bd7c
Tx public key: 465cf787c6048370e424454437f11199ed12df68d60ba30e8bbbb4990e5cc7c6
Timestamp: 1684940457 Timestamp [UCT]: 2023-05-24 15:00:57 Age [y:d:h:m:s]: 02:168:17:01:29
Block: 767150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640367 RingCT/type: yes/0
Extra: 01465cf787c6048370e424454437f11199ed12df68d60ba30e8bbbb4990e5cc7c602110000000633af99f4000000000000000000

1 output(s) for total of 1.762437679000 dcy

stealth address amount amount idx
00: a5c3ee9021b26e7cccb26e1786c0803793dc2fa57988e0e11c3ea4cc97df39aa 1.762437679000 1216255 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": 767160, "vin": [ { "gen": { "height": 767150 } } ], "vout": [ { "amount": 1762437679, "target": { "key": "a5c3ee9021b26e7cccb26e1786c0803793dc2fa57988e0e11c3ea4cc97df39aa" } } ], "extra": [ 1, 70, 92, 247, 135, 198, 4, 131, 112, 228, 36, 69, 68, 55, 241, 17, 153, 237, 18, 223, 104, 214, 11, 163, 14, 139, 187, 180, 153, 14, 92, 199, 198, 2, 17, 0, 0, 0, 6, 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