Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24cfe8cbd6385549b232411e8119bae72efcbf6a6905e1566c53455b4870574

Tx prefix hash: 148c244069ee3d5d1cec9de1ec54c159704c1cecdcfb311888faec0fe949a3ca
Tx public key: 1b671016c0e0a68b7d7c4501f91c3c532281271d1ca3c3469bd53a683c71a522
Timestamp: 1722240430 Timestamp [UCT]: 2024-07-29 08:07:10 Age [y:d:h:m:s]: 00:236:19:06:35
Block: 1076130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169139 RingCT/type: yes/0
Extra: 011b671016c0e0a68b7d7c4501f91c3c532281271d1ca3c3469bd53a683c71a522021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fc67ca2792abd0de9e82e302f70441459be9a7872b1edb53f936cfe6fe31a7d 0.600000000000 1548665 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": 1076140, "vin": [ { "gen": { "height": 1076130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc67ca2792abd0de9e82e302f70441459be9a7872b1edb53f936cfe6fe31a7d" } } ], "extra": [ 1, 27, 103, 16, 22, 192, 224, 166, 139, 125, 124, 69, 1, 249, 28, 60, 83, 34, 129, 39, 29, 28, 163, 195, 70, 155, 213, 58, 104, 60, 113, 165, 34, 2, 17, 0, 0, 0, 4, 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