Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0dd3be2df5b0d7c00c1cd63233f673dadcdaff43118e25d826f9df94519c76

Tx prefix hash: db63d9e3327bf40d61ea294cfdf1198cceb02b3a035dbff3394857fe71fbc2eb
Tx public key: 8885610b37aaf46301a118d413b4dc7f1a88bd5d0c18671a146a2746c225e71e
Timestamp: 1723802355 Timestamp [UCT]: 2024-08-16 09:59:15 Age [y:d:h:m:s]: 00:068:00:28:42
Block: 1089077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48692 RingCT/type: yes/0
Extra: 018885610b37aaf46301a118d413b4dc7f1a88bd5d0c18671a146a2746c225e71e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00cb844ba801c9a32fbf497aeddb69675744120ab7bb8cbb62671b2a8b15bacb 0.600000000000 1563696 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": 1089087, "vin": [ { "gen": { "height": 1089077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00cb844ba801c9a32fbf497aeddb69675744120ab7bb8cbb62671b2a8b15bacb" } } ], "extra": [ 1, 136, 133, 97, 11, 55, 170, 244, 99, 1, 161, 24, 212, 19, 180, 220, 127, 26, 136, 189, 93, 12, 24, 103, 26, 20, 106, 39, 70, 194, 37, 231, 30, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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