Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a10c0cb682236a2d4b15a9dc8a89a49ca5d584bf637a92fa40c8c3e8390015

Tx prefix hash: 1fb3603b636b7a8fe38a8948b409b513e127df9cd09cdb54ea1bb35e9211bbda
Tx public key: 573b9172fb6fe27d0ddb743fff245ce4ad12d122169095d9394090856d1a36e2
Timestamp: 1732167660 Timestamp [UCT]: 2024-11-21 05:41:00 Age [y:d:h:m:s]: 00:130:15:55:38
Block: 1158324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93213 RingCT/type: yes/0
Extra: 01573b9172fb6fe27d0ddb743fff245ce4ad12d122169095d9394090856d1a36e2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2581969a542e1326b05d9c561fde79c4dc9e0add5fa82de30536ed57017fa8eb 0.600000000000 1643953 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": 1158334, "vin": [ { "gen": { "height": 1158324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2581969a542e1326b05d9c561fde79c4dc9e0add5fa82de30536ed57017fa8eb" } } ], "extra": [ 1, 87, 59, 145, 114, 251, 111, 226, 125, 13, 219, 116, 63, 255, 36, 92, 228, 173, 18, 209, 34, 22, 144, 149, 217, 57, 64, 144, 133, 109, 26, 54, 226, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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