Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a34b7516fd9257746439d9a3f81033f1f08db3e397919190cebcaee931d047a

Tx prefix hash: 445561b8be3c14319c00c34e931f3717c0eba34eb9542f625c9c340a23d172ef
Tx public key: 79809d3f5d862af5718dee38d329a18c454df60592a651e0a1345500d4f6d350
Timestamp: 1708028837 Timestamp [UCT]: 2024-02-15 20:27:17 Age [y:d:h:m:s]: 01:070:14:48:00
Block: 958296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311534 RingCT/type: yes/0
Extra: 0179809d3f5d862af5718dee38d329a18c454df60592a651e0a1345500d4f6d35002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d89a0b0eccbc313b886953d3366b43219743ca96cf1e91e0fee62fe6607e13a 0.600000000000 1417655 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": 958306, "vin": [ { "gen": { "height": 958296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d89a0b0eccbc313b886953d3366b43219743ca96cf1e91e0fee62fe6607e13a" } } ], "extra": [ 1, 121, 128, 157, 63, 93, 134, 42, 245, 113, 141, 238, 56, 211, 41, 161, 140, 69, 77, 246, 5, 146, 166, 81, 224, 161, 52, 85, 0, 212, 246, 211, 80, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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