Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b24ce1edb64ea0120012c276796ef31f0acd6468f30c324a6ec527a58861a9

Tx prefix hash: 42f24eb6bd614d8fc652ce84b71170196ae7c3965d4659636eb6ace598641766
Tx public key: 6c6a58a8ec3a59c5bee7b434d5114f7d5a7643582e9e2275a8d64d2bdefd8818
Timestamp: 1721611697 Timestamp [UCT]: 2024-07-22 01:28:17 Age [y:d:h:m:s]: 00:266:20:42:12
Block: 1070908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190650 RingCT/type: yes/0
Extra: 016c6a58a8ec3a59c5bee7b434d5114f7d5a7643582e9e2275a8d64d2bdefd8818021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69128d4c19e382a326ff26dafc314956de863bc5b591af7095a7becd6d77ab21 0.600000000000 1542935 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": 1070918, "vin": [ { "gen": { "height": 1070908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69128d4c19e382a326ff26dafc314956de863bc5b591af7095a7becd6d77ab21" } } ], "extra": [ 1, 108, 106, 88, 168, 236, 58, 89, 197, 190, 231, 180, 52, 213, 17, 79, 125, 90, 118, 67, 88, 46, 158, 34, 117, 168, 214, 77, 43, 222, 253, 136, 24, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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